Mobile device communication

ABSTRACT

Described is a technology by which a mobile computing device such as a mobile telephone operates differently based on detected proximity to another mobile device with which the first mobile device has a defined relationship. For example, the first mobile device may transfer content to the second mobile computing device when proximity corresponds to a non-cellular communications coupling, such as Bluetooth® or Wi-Fi coupling. In this manner, content transfer is deferred until a non-cellular coupling exists. The mobile device (or both devices) may output a notification to indicate that the other mobile computing device has been detected within a threshold proximity, such as via GPS data or by being within the same cellular tower. The type and/or settings of an output notification may vary based on different thresholds.

BACKGROUND

Mobile telephones are no longer simply communication devices. Forexample, mobile telephones can maintain and provide access to mediafiles (e.g., photographs, music, or video). Moreover, some mobiletelephones have GPS (global positioning system) technology or similartechnology that is related to providing location information.

Mobile telephones are thus becoming more like hybrids of communication,computing and other electronic devices. However, while beneficial to theowner of the mobile telephone, there have been no particularconsiderations given to relationships between different mobiletelephones with respect to such capabilities.

SUMMARY

This Summary is provided to introduce a selection of representativeconcepts in a simplified form that are further described below in theDetailed Description. This Summary is not intended to identify keyfeatures or essential features of the claimed subject matter, nor is itintended to be used in any way that would limit the scope of the claimedsubject matter.

Briefly, various aspects of the subject matter described herein aredirected towards a technology by which a mobile computingdevice/telephone operates differently based on detected proximity toanother mobile device with which the first mobile device has a definedrelationship. For example, the first mobile device may configure itselfto transfer content to the second mobile computing device when proximitycorresponds to a non-cellular communications coupling, such asBluetooth® or Wi-Fi. Alternatively, or in addition to, the mobile device(or both devices) may output a notification to indicate that the othermobile computing device has been detected within a threshold proximity,such as via GPS data or by being within the same cellular tower.

In one aspect, a first mobile telephone includes a proximity detectorthat detects proximity with a second mobile telephone with which thefirst mobile telephone has a defined relationship. Proximity logiccoupled to the proximity detector changes an operation of the firstmobile telephone when proximity with the second mobile telephone isdetected. The proximity detector may comprise a monitor that monitorsthe status of a non-cellular communications coupling between the firstmobile telephone and the second mobile telephone. The proximity detectormay also comprise a communication module that monitors location data(e.g., GPS or cellular tower data) sent to the first mobile telephone.

The proximity logic may include comprise a process manager that locatescontent to send from the first mobile telephone to the second mobiletelephone, and a transmission module coupled to the process manager thatsends the content. The proximity logic may include an action controllerthat computes from location data received at the proximity detectorwhether the second mobile telephone is within a thresholddistance-related proximity of the first mobile telephone, and a statusmanager coupled to the action controller that determines whether tooutput a proximity notification. The determination as to whether tooutput a notification may include determining whether a notificationfunction is active, and/or determining whether a time for outputting thenotification is reached.

Other advantages may become apparent from the following detaileddescription when taken in conjunction with the drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

The present invention is illustrated by way of example and not limitedin the accompanying figures in which like reference numerals indicatesimilar elements and in which:

FIG. 1 is a block diagram representing an example communicationsenvironment in which mobile telephones communicate with one another.

FIG. 2 is a representation of example components within a mobiletelephone by which content may be selectively transferred to anothermobile telephone based on a defined relationship between mobiletelephones and proximity comprising a short range non-cellularcommunications coupling.

FIG. 3 is a representation of example components within a mobiletelephone by which a notification may be output based upon proximity toanother mobile telephone with which a relationship has been defined.

FIG. 4 is a flow diagram representing example steps taken to transfercontent from one mobile telephone to another mobile telephone based on adefined relationship between the mobile telephones and proximitycomprising a short range non-cellular communications coupling.

FIG. 5 is a flow diagram representing example steps taken to output anotification on a mobile telephone based on a defined relationshipbetween the mobile telephone and another mobile telephone, and aproximity detected between the telephones.

FIG. 6 shows an illustrative example of a computing and communicationdevice into which various aspects of the present invention may beincorporated.

DETAILED DESCRIPTION

Various aspects of the technology described herein are generallydirected towards operations performed on a mobile telephone (includingother wireless communication devices) when in a defined proximityrelationship with one another mobile telephone. In general, examples ofsuch operations based on proximity relationships as described herein aredirected towards content (e.g., media) sharing and outputtingnotifications.

As will be understood, proximity may be defined in different ways withrespect to different functionality. For example, proximity may bedistance based, but need not be an actual distance, e.g., proximity maymean within Bluetooth® range or other wired or wireless range, beingcoupled to the same LAN, being within a certain GPS-defined distance,being within range of the same cell tower or certain set of towers, andso forth. Further, while the examples herein are primarily describedwith respect to a relationship between two mobile telephones, it isunderstood that any practical number of mobile telephones or likecommunication-capable devices may share information and/or outputinformation in the manner described herein. Still further, theexemplified operations may be based on proximity relationships betweenmobile telephones, but other wireless and even landline-coupled devices(e.g., computers and landline telephones) may also benefit from thevarious aspects described herein with respect to proximityrelationships.

As such, the present invention is not limited to any particularembodiments, aspects, concepts, structures, functionalities or examplesdescribed herein. Rather, any of the embodiments, aspects, concepts,structures, functionalities or examples described herein arenon-limiting, and the present invention may be used various ways thatprovide benefits and advantages in mobile devices and communication ingeneral.

Turning to FIG. 1, there is shown a pair of mobile telephones,exemplified as mobile telephone A 102 and mobile telephone B 104, whichoperate in a relationship with one another. The relationship may be userdefined, or may be defined in advance, e.g., as a pair of telephonespurchased together and programmed by the manufacturer or serviceprovider to have such a relationship.

As described below, when a proximity detector 106 of the mobiletelephone A 102 detects that the mobile telephone B 104 is within acertain proximity, the proximity detector 106 triggers proximity logic108 to possibly modify the operation of the mobile telephone A 102. Theproximity logic 108 is typically an operating system component, but maybe a separate component such as a standalone application program, forexample. Note that the proximity detector 106 need not directly triggerthe proximity logic 108, but can instead regularly (or otherwise) reportlocation or other information to the proximity logic 108, which can thentrigger its logic operations as appropriate. Further note that mobiletelephone B 104 typically includes a similar proximity detector andproximity logic.

As represented in FIG. 1, the mobile telephones 102 and 104 are capableof communicating via one or more cellular towers 110. As alsorepresented by the communications link labeled 112, the mobiletelephones 102 and 104 may be capable of communicating via a short rangenon-cellular communications coupling, such as via a Bluetooth® or Wi-Filink.

FIG. 2 shows an aspect of proximity detection with respect to one typeof operation, which is related to content sharing. In general, anapplication program (of applications 216) or the like adds content suchas media to a content list 218. The application is typically anindependent component, and refers to any application or other code thatneeds to send content such as media data to another mobile device. Inone implementation, the content list 218 comprises a buffer (e.g., afolder) in which the content files to be transferred are kept, alongwith a file name list. Alternatively, content to be sent may bemaintained in its current location on the device, and accessed as neededvia a reference corresponding to that current location.

By way of example, a user viewing a photograph such as a .jpg file mayspecify from a viewing application program that the .jpg file (or anidentifier of the file) be added to the content list 218. The user mayspecify that the content be transmitted to a particular device (e.g., tothe mobile telephone B or to a server to which the mobile telephone Bwill connect, as represented by block 105), or the transmission may beautomatically set up for a destination, such as the mobile telephone Bby default if no other recipients are specified or known. For example,there may a “send-to-telephone B” folder. The content may be buffered ormay be accessed by a reference to its current location.

Unlike conventional data transfer, however, unless specifically directedby the user to send the content (e.g., via GPRS), the proximity detector106 and proximity logic 108 defer sending the content until aproximity-based, short range non-cellular connection (communicationscoupling) is established between the source (mobile telephone A 102) andthe destination (block 105). In this way, there is no cost related tosending the content, e.g., there are no minutes or other GPRS chargesthat are incurred when sending and/or receiving the content.

To this end as generally represented in FIG. 2, the proximity detector106 includes a monitor 220 that monitors the status of a short-rangenon-cellular connection between the mobile telephone A 102 and themobile telephone B 104 (or a server as represented by the block 105).For example, the connection may be a Bluetooth® connection, or a LANconnection, such as a wireless LAN shared by both devices. Otherconnections, such as an infrared or FM link, are also detectable and maybe used for content sharing. GPS-based proximity may also be used.

If a server is used as an intermediate transfer mechanism, an indirectconnection may be established as the coupling, e.g., the mobiletelephone A 102 may transfer the content to the server, which thentransfers the content to the mobile telephone B 104 when the mobiletelephone B establishes or has a connection with the server. Note thatby “short range,” it is only meant that each device can couple to acommunications medium by non-cellular connections; for example aninternet connection may be available to each mobile telephone via ashort range connection, whereby a communications coupling may be madeeven though the two mobile telephones may be very physically distantfrom one another, and possibly outside of any cellular service area.

In any event, when a non-cellular communications coupling betweenrelated devices is determined or the ability to establish a non-cellularcoupling is determined and one is set up, the monitor 220 sends a signalto a process manager component 222 of the proximity logic 108. Note thatdefined relationships between devices may be determined from a list 221of one or more related devices.

In general, the process manager 222 controls the process of push sharingmedia content to the other device, the mobile telephone B or server(block 105). To this end, the process manager 222 communicates with atransmission module 224 and accesses the content list 218, e.g., a medialist database 226. If content is ready for transmission to the specifiedrecipient device, the content is transferred via the transmission module224.

In this example, the process manager 222 controls the status of thetransmission and decides when to start/stop the data transferring. Withrespect to transmission, the transmission module 224 gets the data (oran identifier corresponding the file location or the like) from theprocess manager 222 and starts transferring the data. The transmissionmodule 224 notifies the process manager 222 of the transferring statusand result.

When the media transferring finishes successfully, the process manager222 clears the content list 218 with respect to this particularrecipient. Note that partially-successful transmissions or the like maybe partially cleared, e.g., so that only deltas may later be transmittedto complete a content transmission. Further, note that a recipient maybe a “group” of telephones, whereby rather than deleting the file fromcontent list, the file is only deleted from the telephone (ortelephones) in the group to which it was sent, until no recipientsremain or the list is cleared by some other means (e.g., by manualdeletion or expiration). Still further, there may be a time when anon-cellular connection is not necessary to save cellular transmissionexpense. For example, a user may have free (or very inexpensive) minutesduring evenings or weekends, at the end of the billing cycle, and soforth. The content list may be cleared by transferring over GPRS or thelike at such a time.

As can be seen, two mobile telephones thus may thus share content files(such as media files comprising photographs, music, or video). Bysearching for and detecting another device when it is proximate (e.g.,using Wi-Fi or Bluetooth® technology), a communications coupling may beset up and data transferred, using a peer-to-peer relationship ratherthan a cellular (e.g., GPRS) connection. The user can share content anytime the user desires, although transmission of the content file is onlypending, and real transmission deferred until the two phones are insufficiently nearby proximity to establish a non-cellular, peer-to-peerconnection or other coupling.

Turning to another proximity-related operation, namely proximity-basednotification, FIG. 3 shows how the proximity detector 106 and proximitylogic 108 can provide a notification when two related mobile devices arewithin a certain threshold distance of one another. For example, whentwo (or more) people are meeting, generally one person arrives earlierthan the other, and this person would like to know where the otherperson is and how long it will likely take for the other person to getthere. One current solution for is to send a text message or make aphone call. However, this is not always a convenient solution, e.g.,when driving; further, proximity notification may be valuable in manyother situations.

Instead of manually making a telephone call or sending a text message,through GPS or other location-based technology, a mobile telephone mayprovide location information to another mobile telephone. Note thatconsent is a factor, as people with privacy concerns do not necessarilywant others to know their exact locations at all times.

With respect to notification, if one mobile telephone user consents to“push” notify another mobile telephone of a current location, arecipient mobile telephone may provide audible, visible or tactilefeedback to its user, e.g., as settings are controlled by the recipient.The notifying mobile telephone may control how exact the notification iswith respect to a current location and also may notify its user of thenotification being sent, e.g., two related telephones may buzz or makeother sounds when the two related devices are close to each other (suchas within 500-2000 meters), whereby the mobile telephone people knowsthat the other person is nearby, without either party manually doinganything.

With respect to privacy, people may avoid using phone calls or textmessages ask another's location information, as this is intrusive.Instead, a user can configure a mobile telephone to push suchinformation to another. The sender (as well as the receiver) canconfigure the device such that actual location information is notdisclosed, that is, there is only a closeness notification; othermovement information is not known.

In another aspect, the type of notification may vary, such as withdistance. For example, a slow beep, flash and/or buzz may occur when auser is within 2000 meters, a medium fast beep, flash and/or buzz whenwithin 1000 meters, and a fast beep, flash and/or buzz when within 500meters. Anything that can be output and perceived may be changed, e.g.,frequency, color, vibration intensity, length of notification and soforth may change based on measured or otherwise sensed proximity.

For mobile telephones that do not provide GPS support, cell toweridentification (ID) information may be used. Each mobile telephone knowsthe ID of the cell tower to which it is closest, and this cell tower IDmay be automatically exchanged with another telephone to determinewhether they match, in which event both are within a certain proximity.With the cooperation of a service provider, the exchange can be part ofthe control channel information sent between the cell tower andappropriately registered mobile telephones within its range. Further, aset of cellular tower IDs may be used instead of only the same celltower ID, e.g., a user in an adjacent cell tower can notify the relateduser of the adjacent cell location.

Thus, a person's mobile telephone can automatically let another know ofnearby proximity by pushing location information to the other phone.Built-in GPS support may be used for very accurate notification, orcellular tower matching for lesser, but still somewhat reasonableaccuracy.

FIG. 3 provides one general example of a model implementation, in whicha communication module 330 of the proximity detector 106 receiveslocation information 340 of another mobile telephone with which it has adefined relationship. In this example, the communication module 330 alsomay send out its own location information, e.g., GPS or cell towerinformation. A list 321 of one or more defined related devices (whichmay or may not be the same set of devices listed for media transfer inFIG. 2) may be used to control to which devices to send data, as well asto filter out and discard location information received (e.g.,erroneously) from non-related devices.

To send and/or receive data from a related telephone, a text message orother communication (such as via the cellular tower control channel) maybe sent. Alternatively, a sharing location may be maintained in a server(block 305) to which both mobile telephones are configured to sendand/or receive data.

As represented in FIG. 3, a status manager 332 generally manages thestatus of the notification function, such as to determine operationsbased on whether or the notification function is active (turned on) ornot (turned off). Another status operation may include determining howfrequently to notify the users, e.g., if the two phones are close enoughand both users have been recently reminded, another reminder is deferredso as to not make the notification process annoying; notificationfrequency may be user configurable. The status manager 332 may alsodetermine which type of reminder is to be sent to the user (e.g., abuzz, ring, or popped-up image), which as described above may be userconfigurable and also related to the actual detected closeness. Notethat even without user configuration, a current operating mode of amobile device may factor into the type of reminder, e.g., a mobiletelephone set to operate in a normal ring mode may play an audible soundfor a notification, whereas a mobile telephone set to operate in avibrate mode may quietly buzz and vibrate for a notification.

Also represented in FIG. 3 is an action controller 334, which in generaluses the data received from the other phone's communication module todecide whether to take action or not (or what type of action) based onsome calculation. For example, if GPS data is received as the locationdata 340 from the other mobile telephone and the current mobiletelephone's GPS data is known, a distance calculation may be made by theaction controller 334. If the computed distance is below a certainthreshold, a notification may be output; (as described above, the typeand/or settings of the notification may be varied based on differentthreshold measurements).

For cell tower ID-based location data 340, if the two phones are usingthe same cell tower, then the action controller 332 may provide anotification. As also described above, the type and/or settings of anotification may be varied based on whether a distance or otherproximity (e.g., adjacent) relationship is known between differentcellular tower IDs.

Turning to an explanation of example proximity-based operation changes,FIG. 4 provides an example workflow for proximity-sensed media transfer,and FIG. 5 provides an example workflow for proximity-sensednotification.

In FIG. 4, beginning at step 402 when two phones with a definedrelationship are not yet connected (such as because they are not inclose proximity), one or more applications each may send (or identify) acontent file, which is added to the content list for later transfer.Step 402 represents waiting for the related telephone (or server towhich the related telephone will likely couple) to be detected via themonitor as being in proximity, e.g., within Bluetooth® range or able toconnect to one another via a wireless LAN or other non-cellular means,for example. Step 404 also represents an override option, in which auser specifies that the content file is to be sent to a particularmobile telephone (e.g., via GPRS or other cellular connection)regardless of any proximity-based non-cellular connection status. Manualoverride and/or automatic override (e.g., based on time of day) may beused.

Step 406 represents the monitor recognizing the related telephone asbeing in its related telephone list, such as via a unique identifier,(which may be the other telephone's phone number). For example, usingthe example modules of FIG. 2, at step 406 the monitor 220 tells theprocess manager 222 that the other mobile telephone is nearby, and tellsthe process manager 222 the name (identity) of the other phone. From theuser's perspective, the name may be a user-friendly name, converted to aunique identity or the like by the logic.

Step 408 evaluates (e.g., in the process manager 222) whether there areany content files pending for transfer to the related telephone. Step410 represents making the coupling, although as can be readilyappreciated, a connection process may be started as soon as the relatedtelephone was detected at step 404, and indeed, a connection may havebeen automatic and used in making the detection.

If there is at least one content file to be sent, at step 410 theprocess manager 222 sends the content file (or an identifier thereof bywhich the file may be accessed) to the transmission module 224, andtells the transmission module 224 the identity of the recipient mobiletelephone (or server).

Step 414 represents the transmission module transferring the data. Ifthe data was sent successfully, at step 416 the transmission module 224notifies the process manager 222 that the data was sent out and at step418 the process manager 222 removes the data file from the content list.As described above, an unsuccessful transmission (e.g., the connectionwas broken) can result in the entire data file being re-sent, or somepart thereof being re-sent, provided the transmission file is capable ofinforming the process manager as to what part (or parts) wassuccessfully sent, and the recipient can accept partial data and buildup the content file.

With respect to an example proximity-based workflow for notifications,FIG. 5 shows example steps beginning at step 502 where locationinformation is received at one mobile telephone from a telephone havinga defined relationship therewith for notifications. Step 504 representsevaluating whether the notification function is active, which if not,basically ignores the received location information.

If the notification function is active, step 506 is executed to performthe threshold proximity evaluation. As described above, thisdetermination may be made with GPS data, may be by cellular tower ID, orsome other location-related data. As also described above, there may bedifferent thresholds that result in different types of notifications,however in any event, at least a minimum threshold may be requiredbefore some notification is made. If not met, the process basicallydiscards the location data, at least with respect to issuing anotification.

Step 508 represents evaluating the notification frequency, e.g., whethera notification is to be issued or not depending on how recently aprevious notification was issued. The time may vary dependent on a typeof notification, e.g., a very close proximity may have a shorter timethan a relatively distant proximity. Further, the time may be variedbased on which threshold was met, e.g., if a sender has crossed athreshold so as to now be closer than a previously computed threshold, anew notification may be sent regardless of the last time a notificationwas sent. Although the simplified workflow of FIG. 5 representsreturning to step 502 if the notification time requirement is not met,it can be readily appreciated that step 508 may also delay until thetime requirement is met, e.g., if location information is only sent onceper minute and the time for the next notification is less than oneminute, the notification can be delayed until due (or even immediatelyoutput) based on the knowledge that another set of location data willnot be received until after the notification is due.

If a notification is to be output, step 510 represents outputting thenotification according to the current device settings. The notificationmay be any of an audible, tactile or visual output, which may be userconfigurable, threshold dependent, and so forth. An acknowledgement orcounterpart notification may be provided to the sender.

Exemplary Operating Environment

FIG. 6 illustrates an example of a suitable mobile device 600 on whichaspects of the subject matter described herein may be implemented. Themobile device 600 is only one example of a device and is not intended tosuggest any limitation as to the scope of use or functionality ofaspects of the subject matter described herein. Neither should themobile device 600 be interpreted as having any dependency or requirementrelating to any one or combination of components illustrated in theexemplary mobile device 600.

With reference to FIG. 6, an exemplary device for implementing aspectsof the subject matter described herein includes a mobile device 600. Insome embodiments, the mobile device 600 comprises a cell phone, ahandheld device that allows voice communications with others, some othervoice communications device, or the like. In these embodiments, themobile device 600 may be equipped with a camera for taking pictures,although this may not be required in other embodiments. In otherembodiments, the mobile device 600 comprises a personal digitalassistant (PDA), hand-held gaming device, notebook computer, printer,appliance including a set-top, media center, or other appliance, othermobile devices, or the like. In yet other embodiments, the mobile device600 may comprise devices that are generally considered non-mobile suchas personal computers, servers, or the like.

Components of the mobile device 600 may include, but are not limited to,a processing unit 605, system memory 610, and a bus 615 that couplesvarious system components including the system memory 610 to theprocessing unit 605. The bus 615 may include any of several types of busstructures including a memory bus, memory controller, a peripheral bus,and a local bus using any of a variety of bus architectures, and thelike. The bus 615 allows data to be transmitted between variouscomponents of the mobile device 600.

The mobile device 600 may include a variety of computer-readable media.Computer-readable media can be any available media that can be accessedby the mobile device 600 and includes both volatile and nonvolatilemedia, and removable and non-removable media. By way of example, and notlimitation, computer-readable media may comprise computer storage mediaand communication media. Computer storage media includes volatile andnonvolatile, removable and non-removable media implemented in any methodor technology for storage of information such as computer-readableinstructions, data structures, program modules, or other data. Computerstorage media includes, but is not limited to, RAM, ROM, EEPROM, flashmemory or other memory technology, CD-ROM, digital versatile disks (DVD)or other optical disk storage, magnetic cassettes, magnetic tape,magnetic disk storage or other magnetic storage devices, or any othermedium which can be used to store the desired information and which canbe accessed by the mobile device 600.

Communication media typically embodies computer-readable instructions,data structures, program modules, or other data in a modulated datasignal such as a carrier wave or other transport mechanism and includesany information delivery media. The term “modulated data signal” means asignal that has one or more of its characteristics set or changed insuch a manner as to encode information in the signal. By way of example,and not limitation, communication media includes wired media such as awired network or direct-wired connection, and wireless media such asacoustic, RF, infrared, Wi-Fi, WiMAX, and other wireless media.Combinations of any of the above should also be included within thescope of computer-readable media.

The system memory 610 includes computer storage media in the form ofvolatile and/or nonvolatile memory and may include read only memory(ROM) and random access memory (RAM). On a mobile device such as a cellphone, operating system code 620 is sometimes included in ROM although,in other embodiments, this is not required. Similarly, applicationprograms 625 are often placed in RAM although again, in otherembodiments, application programs may be placed in ROM or in othercomputer-readable memory. The heap 630 provides memory for stateassociated with the operating system 620 and the application programs625. For example, the operating system 620 and application programs 625may store variables and data structures in the heap 630 during theiroperations.

The mobile device 600 may also include other removable/non-removable,volatile/nonvolatile memory. By way of example, FIG. 6 illustrates aflash card 635, a hard disk drive 636, and a memory stick 637. The harddisk drive 636 may be miniaturized to fit in a memory slot, for example.The mobile device 600 may interface with these types of non-volatileremovable memory via a removable memory interface 631, or may beconnected via a universal serial bus (USB), IEEE 6394, one or more ofthe wired port(s) 640, or antenna(s) 665. One of the antennas 665 mayreceive GPS data. In these embodiments, the removable memory devices635-137 may interface with the mobile device via the communicationsmodule(s) 632. In some embodiments, not all of these types of memory maybe included on a single mobile device. In other embodiments, one or moreof these and other types of removable memory may be included on a singlemobile device.

In some embodiments, the hard disk drive 636 may be connected in such away as to be more permanently attached to the mobile device 600. Forexample, the hard disk drive 636 may be connected to an interface suchas parallel advanced technology attachment (PATA), serial advancedtechnology attachment (SATA) or otherwise, which may be connected to thebus 615. In such embodiments, removing the hard drive may involveremoving a cover of the mobile device 600 and removing screws or otherfasteners that connect the hard drive 636 to support structures withinthe mobile device 600.

The removable memory devices 635-637 and their associated computerstorage media, discussed above and illustrated in FIG. 6, providestorage of computer-readable instructions, program modules, datastructures, and other data for the mobile device 600. For example, theremovable memory device or devices 635-637 may store images taken by themobile device 600, voice recordings, contact information, programs, datafor the programs and so forth.

A user may enter commands and information into the mobile device 600through input devices such as a key pad 641 and the microphone 642. Insome embodiments, the display 643 may be touch-sensitive screen and mayallow a user to enter commands and information thereon. The key pad 641and display 643 may be connected to the processing unit 605 through auser input interface 650 that is coupled to the bus 615, but may also beconnected by other interface and bus structures, such as thecommunications module(s) 632 and wired port(s) 640.

A user may communicate with other users via speaking into the microphone642 and via text messages that are entered on the key pad 641 or a touchsensitive display 643, for example. The audio unit 655 may provideelectrical signals to drive the speaker 644 as well as receive anddigitize audio signals received from the microphone 642.

The mobile device 600 may include a video unit 660 that provides signalsto drive a camera 661. The video unit 660 may also receive imagesobtained by the camera 661 and provide these images to the processingunit 605 and/or memory included on the mobile device 600. The imagesobtained by the camera 661 may comprise video, one or more images thatdo not form a video, or some combination thereof.

The communication module(s) 632 may provide signals to and receivesignals from one or more antenna(s) 665. One of the antenna(s) 665 maytransmit and receive messages for a cell phone network. Another antennamay transmit and receive Bluetooth® messages. Yet another antenna (or ashared antenna) may transmit and receive network messages via a wirelessEthernet network standard.

In some embodiments, a single antenna may be used to transmit and/orreceive messages for more than one type of network. For example, asingle antenna may transmit and receive voice and packet messages.

When operated in a networked environment, the mobile device 600 mayconnect to one or more remote devices. The remote devices may include apersonal computer, a server, a router, a network PC, a cell phone, apeer device or other common network node, and typically includes many orall of the elements described above relative to the mobile device 600.

Aspects of the subject matter described herein are operational withnumerous other general purpose or special purpose computing systemenvironments or configurations. Examples of well known computingsystems, environments, and/or configurations that may be suitable foruse with aspects of the subject matter described herein include, but arenot limited to, personal computers, server computers, hand-held orlaptop devices, multiprocessor systems, microcontroller-based systems,set top boxes, programmable consumer electronics, network PCs,minicomputers, mainframe computers, distributed computing environmentsthat include any of the above systems or devices, and the like.

Aspects of the subject matter described herein may be described in thegeneral context of computer-executable instructions, such as programmodules, being executed by a mobile device. Generally, program modulesinclude routines, programs, objects, components, data structures, and soforth, which perform particular tasks or implement particular abstractdata types. Aspects of the subject matter described herein may also bepracticed in distributed computing environments where tasks areperformed by remote processing devices that are linked through acommunications network. In a distributed computing environment, programmodules may be located in both local and remote computer storage mediaincluding memory storage devices.

Furthermore, although the term server is often used herein, it will berecognized that this term may also encompass a client, a set of one ormore processes distributed on one or more computers, one or morestandalone storage devices, a set of one or more other devices, acombination of one or more of the above, and the like.

CONCLUSION

While the invention is susceptible to various modifications andalternative constructions, certain illustrated embodiments thereof areshown in the drawings and have been described above in detail. It shouldbe understood, however, that there is no intention to limit theinvention to the specific forms disclosed, but on the contrary, theintention is to cover all modifications, alternative constructions, andequivalents falling within the spirit and scope of the invention.

The invention claimed is:
 1. A method comprising: at a time when anon-cellular connection is unavailable between a first mobile computingdevice and a second mobile computing device, receiving an indication onthe first mobile computing device identifying a data file stored on thefirst mobile computing device to send to the second mobile computingdevice upon future establishment of the non-cellular connection;monitoring availability of the non-cellular connection between the firstmobile computing device and the second mobile computing device; in afirst instance, responsive to detecting that the non-cellular connectionis available between the first mobile computing device and the secondmobile computing device, using the non-cellular connection to send thedata file stored on the first mobile computing device from the firstmobile computing device to the second mobile computing device; and in asecond instance, using cellular communication instead of thenon-cellular connection to send other data files stored on the firstmobile computing device from the first mobile computing device to thesecond mobile computing device.
 2. The method of claim 1, thenon-cellular connection comprising a frequency-modulated link.
 3. Themethod of claim 1, the non-cellular connection comprising a direct linkbetween the first mobile computing device and the second mobilecomputing device.
 4. The method of claim 3, the direct link being ashort-range wireless connection having an associated physical rangelimitation for direct communication between the first mobile computingdevice and the second mobile computing device.
 5. The method of claim 4,the direct link having a different frequency band than the cellularcommunication.
 6. The method of claim 1, further comprising: providingan option whether to use the cellular communication to send the otherdata files when the non-cellular connection is not available; receivinginput accepting the option to use the cellular communication to send theother data files when the non-cellular connection is not available; andusing the cellular communication to send the other data files in thesecond instance based at least on the input accepting the option.
 7. Themethod of claim 1, further comprising: monitoring the availability ofthe non-cellular connection based at least on physical proximity of thefirst mobile computing device to the second mobile computing device. 8.The method of claim 7, further comprising: obtaining a location of thefirst mobile computing device via Global Positioning Systemfunctionality of the first mobile computing device.
 9. A mobilecomputing device comprising: a hardware processing unit; and a hardwarecomputer storage medium storing computer-readable instructions which,when executed by the hardware processing unit, cause the hardwareprocessing unit to: at a time when non-cellular communication isunavailable between the mobile computing device and a first other mobilecomputing device, identify a first data file stored on the mobilecomputing device to send to the first other mobile computing device at afuture time when the non-cellular communication between the mobilecomputing device and the first other mobile computing device isavailable; after identifying the first data file, monitor availabilityof the non-cellular communication between the mobile computing deviceand the first other mobile computing device; responsive to detectingavailability of the non-cellular communication between the mobilecomputing device and the first other mobile computing device, send thefirst data file from the mobile computing device to the first othermobile computing device using the non-cellular communication instead ofcellular communication; identify a second data file stored on the mobilecomputing device to send to a second other mobile computing device forwhich the non-cellular communication with the mobile computing device isnot available; and send the second data file from the mobile computingdevice to the second other mobile computing device using the cellularcommunication instead of the non-cellular communication.
 10. The mobilecomputing device of claim 9, wherein the computer-readable instructions,when executed by the hardware processing unit, cause the hardwareprocessing unit to: display a notification that the first other mobilecomputing device is available via the non-cellular communication. 11.The mobile computing device of claim 10, the notification comprisingchanging a color displayed on the mobile computing device.
 12. Themobile computing device of claim 9, wherein the computer-readableinstructions, when executed by the hardware processing unit, cause thehardware processing unit to: determine a specified time of day when thecellular communication is used for message communication; and defersending the second data file to the second other mobile computing deviceuntil the specified time of day.
 13. The mobile computing device ofclaim 9, the first data file comprising a first image file and thesecond data file comprising a second image file.
 14. The mobilecomputing device of claim 9, wherein the non-cellular communication isperformed over a wireless link that directly connects the mobilecomputing device and the first other mobile computing device.
 15. Amobile computing device comprising: a hardware processing unit; and ahardware computer storage medium storing computer-readable instructionswhich, when executed by the hardware processing unit, cause the hardwareprocessing unit to: identify a second mobile computing device with whichto communicate; at a time when a non-cellular connection is unavailablebetween the mobile computing device and the second mobile computingdevice, receive user input identifying a first data file stored on themobile computing device to send to the second mobile computing deviceupon future establishment of the non-cellular connection; afterreceiving the user input identifying the first data file, monitoravailability of the non-cellular connection between the mobile computingdevice and the second mobile computing device; in a first instance,responsive to detecting that the non-cellular connection between themobile computing device and the second mobile computing device hasbecome available, use the non-cellular connection instead of cellularcommunication to send the first data file from the mobile computingdevice to the second mobile computing device; and in a second instance,use the cellular communication instead of the non-cellular connection tosend a second data file stored on the mobile computing device from themobile computing device to the second mobile computing device.
 16. Themobile computing device of claim 15, wherein the computer-readableinstructions, when executed by the hardware processing unit, cause thehardware processing unit to: monitor the availability of thenon-cellular connection between the mobile computing device and thesecond mobile computing device using non-cellular signaling to detectproximity of the second mobile computing device to the mobile computingdevice; and when the non-cellular signaling indicates that the secondmobile computing device is within a specified proximity of the mobilecomputing device, use the non-cellular connection to send the first datafile.
 17. The mobile computing device of claim 15, the non-cellularconnection being a wireless peer-to-peer connection.
 18. The mobilecomputing device of claim 15, wherein the computer-readableinstructions, when executed by the hardware processing unit, cause thehardware processing unit to: determine a first location of the mobilecomputing device; obtain a second location of the second mobilecomputing device; and monitor the availability of the non-cellularconnection based at least on the first location and the second location.19. The mobile computing device of claim 15, wherein thecomputer-readable instructions, when executed by the hardware processingunit, cause the hardware processing unit to: identify a first cell towerthat is closest to the mobile computing device; identify a second celltower that is closest to the second mobile computing device; and monitorthe availability of the non-cellular connection based at least on thefirst cell tower and the second cell tower.
 20. The mobile computingdevice of claim 15, programmed by a manufacturer of the mobile computingdevice to have a predefined relationship with the second mobilecomputing device.